SEO: FAQ limitations questions H2 (deep-link anchors) - #227
Open
eyalb181 wants to merge 1 commit into
Open
Conversation
The questions in faq/limitations.md used H4 (####), but GitBook only generates heading anchors for H1-H3 — so they weren't deep-linkable and weren't in the page outline (unlike faq/general and faq/comparisons which use H2). Promote them to H2: anchored, in the outline, sequential under the page-title H1, and consistent with the other FAQ pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The questions in
faq/limitations.mdused H4 (####), but GitBook only generates heading anchors for H1–H3 — so they weren't deep-linkable or in the page outline (unlikegeneral/comparisonswhich use H2). Promoted to H2.🤖 Generated with Claude Code